Originally by: Kazzac Elentria

---

Originally by: Motivated Prophet

---

Originally by: glas mir

---

No BPCs and BPOs look the same to scanners and killboards

---

In the interest of being pedantic-ly correct, there are some exceptions to this that rely on the "Quantity" column not stacking instantiated objects, though they may have been phased out in the new killmail system.

MP

---

Nope, still the same.

I think it was partially discussed in the first CSM when we asked for different colors on BPC and BPOs

Big database issue to try and implement more or less.

---

Originally by: Motivated Prophet

---

Originally by: SencneS

---

Well... they have a "Original" and "Copy" Tag on them, I don't know why they don't just add that column to the kill mail and the scanner results.

No real significant impact on the database other then show an extra column this already exits..

---

You misunderstand. The relevant portions of the DB are:

CREATE TABLE itemdb (
id INT...,
name..., /*Example: "Amarr Shuttle Blueprint"*/
... /* Item static attributes (build costs for blueprints, activation time for an armor hardener, etc.) go here */
);

CREATE TABLE item (
...
item_type ENUM('blueprint',...),
item_id INT...,
itemdb_id INT... REFERENCES itemdb(`id`),
quantity INT...,
container_id INT...
);

CREATE TABLE blueprint_instance (
item_id INT... REFERENCES item(`id`),
copies_remaining INT DEFAULT -1, /*-1 = unlimited*/
...
);

So right now, the query is:
SELECT itemdb.name, item.quantity FROM item, itemdb WHERE item.itemdb_id = itemdb.id AND item.container_id = /*the container you're looking inside, be it a hangar or a wreck or whatever*/;

To add BPC vs. BPO, you'd have to do:
SELECT IF(blueprint_instance.copies_remaining=-1,'original','copy'), itemdb.name, item.quantity FROM item, itemdb LEFT OUTER JOIN blueprint_instance ON blueprint_instance.item_id = item.id WHERE item.itemdb_id = itemdb.id AND item.container_id = /*the container you're looking inside, be it a hangar or a wreck or whatever*/;

With apologies for my probably-incorrect SQL, but you get the idea.

MP

---